Add Bicep description for infra/private-endpoints.bicep #2665
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: pamelafox <[email protected]>
Copilot
AI
changed the title
Copilot finished work on behalf of
pamelafox
August 4, 2025 18:03
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added a
metadata descriptionto theinfra/private-endpoints.bicepfile to help users understand its role in the VPN/private networking story.The description explains that this file creates private endpoints for Azure services and configures Azure Monitor Private Link Scope with DNS zones for secure private networking. This follows the established pattern used by other Bicep files in the repository such as
network-isolation.bicepand files incore/networking/.The
private-endpoints.bicepfile is a key component in the private networking infrastructure that works together with VNet and VPN Gateway configurations to enable secure communication between Azure services within the virtual network.Fixes #1678.
Warning
Firewall rules blocked me from connecting to one or more addresses
I tried to connect to the following addresses, but was blocked by firewall rules:
aka.msbicep build infra/private-endpoints.bicep --stdout(dns block)bicep build infra/main.bicep --stdout(dns block)If you need me to access, download, or install something from one of these locations, you can either:
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.